feat: UniversalResolver v3 support - #3848

🦋 Changeset detected

Latest commit: d6b88f4

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

There might also be an issue with defaulting to eth mainnet's coinType if no coinType is provided — this 'eth mainnet as default' is explicitly deprecated in ENSIP-19 https://docs.ens.domains/ensip/19/#deprecating-mainnet-as-default which tells me that the api surface for reverse resolution requires a coinType (or a chainId from which to derive one). i.e. it's the consumer's responsibility to provide a specific coinType context within which to perform reverse resolution

which tells me that the api surface for reverse resolution requires a coinType (or a chainId from which to derive one). i.e. it's the consumer's responsibility to provide a specific coinType context within which to perform reverse resolution

that’s correct, but we’re also trying to get the latest universal resolver out to as many consumers as possible to allow for a smooth transition to ENSv2.

requiring coinType then turns these changes into breaking changes for the viem API, and it’d probably be better to rip the bandaid off in a breaking change after this migration, to prevent dissuading consumers from updating viem.

Just need to deploy contracts to these chains and update addresses:

• linea
• berachain
• story